Can you update your branch to pick up the fix for the failing CI build?

@ODORA0 is it possible to fix the issue without getting rid the filter?

@samuelmale The filtering restricts options because the shouldFilterItem function dynamically excludes items that don’t match the current inputValue. If the logic doesn’t explicitly account for an empty inputValue (e.g. when the caret is clicked), only the currently selected item or no items may be displayed, as the filter prevents non-matching items from appearing.

Thanks, @ODORA0. How different is this than getting rid of the prop altogether? AFAICT, the filtering behaviour of the ComboBox input where only the matching item is listed when the dropdown is clicked after selecting an item is by design. See the underlying useComboBox hook implementation for the Downshift library here. I think it's preferable to just remove the prop altogether until the underlying behavior changes upstream from Carbon.

@denniskigen I agree, change made

Ping @denniskigen

Good to go for me, @samuelmale.